deps(dev): Bump @bytecodealliance/jco from 1.5.0 to 1.8.1 #2303
Conversation
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
dependabot
bot
added
dependencies
|
Merging to
|
|
New and removed dependencies detected. Learn more about Socket for GitHub ↗︎
🚮 Removed packages: npm/@bytecodealliance/[email protected] |
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat are trivial packages?Packages less than 10 lines of code are easily copied into your own project and may not warrant the additional supply chain risk of an external dependency. Removing this package as a dependency and implementing its logic will reduce supply chain risk. What is new author?A new npm collaborator published a version of the package for the first time. New collaborators are usually benign additions to a project, but do indicate a change to the security surface area of a package. Scrutinize new collaborator additions to packages because they now have the ability to publish code into your dependency tree. Packages should avoid frequent or unnecessary additions or changes to publishing rights. What is network access?This module accesses the network. Packages should remove all network access that is functionally unnecessary. Consumers should audit network access to ensure legitimate use. What is shell access?This module accesses the system shell. Accessing the system shell increases the risk of executing arbitrary code. Packages should avoid accessing the shell which can reduce portability, and make it easier for malicious shell access to be introduced. What is unstable ownership?A new collaborator has begun publishing package versions. Package stability and security risk may be elevated. Try to reduce the number of authors you depend on to reduce the risk to malicious actors gaining access to your supply chain. Packages should remove inactive collaborators with publishing rights from packages on npm. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/bytecodealliance/jco-1.8.1
branch
3 times, most recently
from
4fb864f to
0de74f7
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/bytecodealliance/jco-1.8.1
branch
3 times, most recently
from
aa706aa to
3a467d8
Compare
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/bytecodealliance/jco-1.8.1
branch
4 times, most recently
from
17dbcec to
35b2f64
Compare
Bumps [@bytecodealliance/jco](https://github.com/bytecodealliance/jco) from 1.5.0 to 1.8.1. - [Release notes](https://github.com/bytecodealliance/jco/releases) - [Commits](bytecodealliance/jco@1.5.0...1.8.1) --- updated-dependencies: - dependency-name: "@bytecodealliance/jco" dependency-type: direct:development update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
force-pushed
the
dependabot/npm_and_yarn/bytecodealliance/jco-1.8.1
branch
from
35b2f64 to
bdc9b8e
Compare
Bumps @bytecodealliance/jco from 1.5.0 to 1.8.1.
Release notes
Sourced from
@bytecodealliance/jco's releases.... (truncated)
Commits
19f96301.8.1da41087fix: top-level resource bindgen (#526)791d1c11.8.0dc01f95feat: support top-level resources (#525)9e784e2deps: update to latest Wasmtime@27 toolchain (#524)7b6e386fix(examples): mention wac in string-reverse-upper README (#521)b125d471.7.28f860a8deps: update to [email protected], reenable test (#520)08d7fb8fix: resource map being populated after trampoline (#519)d70b4d4feat(examples): add documentation and walkthroughs for examples (#514)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)